\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f0\b0\i0\ulnone\fs28\fc1\cf1 Q: I'm sending mail via UUCP. Things work
\i great
\i0 from my mail server (which is also my UUCP gateway). From a mail client, though, I get error messages indicating the remote UUCP machine is unknown. The bounce message looks like this:\
\
\f3\b\fs24\li720 Date
\b0 : Mon, 13 Apr 92 13:11:11 CDT\
\b From
\b0 : Mailer-Agent (NeXT Mail Agent)\
\b Subject
\b0 : Returned mail: Unable to deliver mail\
\b To
\b0 : amm\
\f0\fs28 \
----- Transcript of session follows -----\
554 rhino!sandy... Never heard of UUCP host rhino\
\
----- Unsent message follows -----\
…\
\li0 \
What's going on here?\
\
A: One likely source of the problem is that
\b sendmail
\b0 might not have an uptodate notion of the known UUCP connections. If you've added the remote machine (
\b rhino
\b0 in the example, above) and neither rebooted the server nor restarted the
\b sendmail
\b0 process on the server, then
\b sendmail
\b0 doesn't know about the new connection.\
\
A
\b sendmail
\b0 daemon process is started when the system boots, by
\b /etc/rc
\b0 . When
\b sendmail
\b0 starts up, it runs the command
\b uuname
\b0 to determine the known UUCP connections. (At least, it does this with all the standard configuration files NeXT ships.) The
\b uuname
\b0 command is run
\i only once
\i0 . It is this
\b sendmail
\b0 daemon that handles all the mail coming from the client machines.\
\
So, why does mail originating locally work? A new
\b sendmail
\b0 process is run for each locally-originating message; this new
\b sendmail
\b0 process runs its own instance of
\b uuname
\b0 when it starts. Since
\b uuname
\b0 for the new
\b sendmail
\b0 process has been run after the new system's addition to